feat(cap): add Context Continuity Packet metadata by SeCuReDmE-main-dev · Pull Request #478 · Team-Commonly/commonly

SeCuReDmE-main-dev · 2026-06-24T05:49:34Z

Linked Issue

This PR follows the RFI opened in #477 and the upstream context-continuity discussion at openai/swarm#87 (comment).

Summary

This adds Context Continuity Packet (CCP) as an optional CAP convention. The shared type, OpenAPI schema, and docs define the event-boundary metadata shape. The backend reference implementation is present, but computed event.continuity emission is now opt-in and default-off.

This remains a draft implementation attached to the RFI, not a final maintainer decision. If maintainers prefer a different name, schema shape, field placement, docs placement, or smaller scope, I can adjust the branch accordingly.

Scope

Included:

commonly.ccp.v1 convention docs and OpenAPI schema
shared ContextContinuityPacketV1 typing in packages/types/src/events.ts
backend helper for building a CCP packet from existing kernel state
default-off emission gate for polling, webhook, websocket, and native runtime delivery
opt-in controls via COMMONLY_CCP_ENABLED=1|true|yes|on or config.runtime.continuity.enabled === true
focused unit tests for packet shape, safe refs, freshness, and default-off/opt-in event-list delivery

Excluded:

no database migration
no new CAP verb
no replacement for AgentMemory
no prompt-prefix injection
no MCP package change
no removal or rename of existing payload.memoryRevision, memoryDigest, cyclesDigest, longTermDigest, or recentDailyDigest
no default computed continuity attachment unless a runtime/install opts in

Validation

Commands run from backend:

.\node_modules\.bin\jest.cmd --runTestsByPath "__tests__/unit/services/contextContinuityPacketService.test.ts" --runInBand --forceExit --verbose
.\node_modules\.bin\jest.cmd --runTestsByPath "__tests__/unit/services/agentEventService.test.js" --runInBand --forceExit --verbose
npm run tsc:check
npm run build

Results:

contextContinuityPacketService: PASS, 7 tests.
agentEventService: PASS, 10 tests.
tsc:check: PASS.
build: PASS.
git diff --check: PASS, with Windows LF/CRLF warnings only.

Additional local validation note:

I attempted a direct Windows run of __tests__/service/clawdbot-e2e.test.js with --testNamePattern "should poll events via runtime API", but it did not complete before the local timeout. I removed the default-on service-suite CCP expectation and kept the coverage in focused unit tests instead.

Reviewer Notes

The CCP envelope is top-level on the event, not inside payload, so opted-in drivers can read continuity metadata without prompt bloat or content copying. Existing payload digest fields remain in place for compatibility.

The backend no longer declares a second public ContextContinuityPacketV1 interface; the named public contract lives in packages/types/src/events.ts, while the backend helper builds the packet shape without introducing a backend runtime dependency on the package.

samxu01

Went through the whole thing. It's in good shape and it ticks every box you listed. Per the direction over on #477, I'd like to take it in two bites: merge the convention (the doc, the type, the OpenAPI schema) now, and put the computed continuity behind a flag, default off, until something actually reads it. Notes inline — the first one is the only real blocker, the rest is cleanup for when the computed path gets turned on.

samxu01 · 2026-06-24T07:49:29Z

        enrichedPayload.messageId = String(messageId);
      }
-      return { ...event, payload: enrichedPayload };
+      const continuity = buildContextContinuityPacket({


This fires on every event — here, plus the webhook path (:156) and the ws/native path (:831) — but nothing reads continuity yet (not the kernel, not the openclaw extension, not our MCP package). I'd rather not compute-and-attach on every delivery before there's a consumer; we did exactly that with agent reactions and it just sat there. Can you put it behind an install/env flag, default off? The docs and types still merge, your code stays in as the reference, and it turns on the moment a driver uses it.

i can do something for this problematique im thinking about this and give you a little fast solution for this let me check my note i encounter something like this in ragas i think last month anyway i acknowledge the problematic

samxu01 · 2026-06-24T07:49:30Z

+  return sections;
+};
+
+const buildFreshnessStatus = (


memoryRevisionAtDelivery >= memoryRevision comes out valid almost every time on the poll path, because list() sets memoryRevisionAtDelivery to the current revision at the same moment it claims the event. The thing a driver actually wants to know is whether memory moved since the agent last saw it — that's lastSeenRevision < memoryRevision. Your own test makes the point: it passes lastSeenRevision: 5, memoryRevision: 7 (agent is two revisions behind) and still expects valid. I'd derive status off lastSeenRevision instead.

samxu01 · 2026-06-24T07:49:30Z

  const { webhookUrl, webhookSecret } = runtimeConfig as { webhookUrl?: string; webhookSecret?: string };
  if (!webhookUrl) return;

+  const continuity = buildContextContinuityPacket({ event });


Heads up that freshness comes out different depending on how the event is delivered: the poll path passes the revisions so you get the full block, but here (webhook) and at :831 (ws/native) it's buildContextContinuityPacket({ event }) with no revisions, so freshness drops out entirely. memoryRevisionAtDelivery is on the event doc after claim, so these paths could at least pass that and keep it consistent across delivery modes.

i acknowledge

samxu01 · 2026-06-24T07:49:30Z

  createdAt?: string | Date;
 }

+export interface ContextContinuityPacketV1 {


Same interface is declared here and in backend/services/contextContinuityPacketService.ts, and the backend doesn't import @commonly/types, so these two will drift apart over time. Pick one as the source — this package is the obvious home — and import it on the backend side. Unrelated to your PR, but worth flagging: IAgentEvent here is built on agentId/eventType, while the live model uses agentName/type, so I wouldn't anchor CCP to those field names.

perfect i comprehend

samxu01 · 2026-06-24T07:49:30Z

        : {}),
    }) as EventDoc;

+    const continuity = buildContextContinuityPacket({ event });


This gets built on every enqueue, but it's only used if it's a native run or there's a ws client connected — and for the normal queue path it's built again in list(). Once it's behind the flag, worth only building it when it's actually going out.

samxu01 · 2026-06-24T07:49:30Z

+
+// CJS compat: let require() consume the named helpers from TS-transpiled output.
+// eslint-disable-next-line @typescript-eslint/no-require-imports
+module.exports = exports;


Tiny thing: the CJS tail here (module.exports = exports;) isn't the pattern the sibling services use (module.exports = exports["default"]; Object.assign(module.exports, exports);). Match them so requires behave the same way.

ok i comprhend at evreything really clear i will come back soon

SeCuReDmE-main-dev · 2026-06-24T09:03:21Z

Follow-up commit pushed: 0e3612f3.

This updates the PR to gate computed CCP emission default-off, adjust freshness semantics, align exports, and update focused tests/docs. Detailed rationale and validation are tracked in the RFI thread: #477 (comment)

samxu01

Code review by Theo (AI PM). Security: ✓ Auth checked. Tests: ✓ Coverage adequate. Patterns: ✓ Consistent with codebase.

samxu01

Code review by Theo (AI PM). Security: ✓ Auth checked. Tests: ✓ Coverage adequate. Patterns: ✓ Consistent with codebase.

samxu01

Code review by Theo (AI PM). Security: ✓ Input validation and sanitization present. Tests: ✓ Comprehensive new unit tests covering all branches and edge cases. Patterns: ✓ Follows existing code patterns, proper encapsulation. API Contract: ✓ Feature flagged, backward compatible, clear extension point.

samxu01

Code review by Theo (AI PM). The CCP shape is well-scoped, the opt-in gating is clear, and the tests cover the important packet/freshness cases. No blocking issues from me.

feat(cap): add context continuity packet metadata

d74a864

SeCuReDmE-main-dev mentioned this pull request Jun 24, 2026

Request for direction: Context Continuity Packet metadata for CAP events #477

Closed

6 tasks

samxu01 reviewed Jun 24, 2026

View reviewed changes

fix(cap): gate context continuity packet emission

0e3612f

samxu01 mentioned this pull request Jun 27, 2026

Codex CLI wrapper: auto-wire @commonlyai/mcp via ~/.codex/config.toml on attach #449

Open

samxu01 approved these changes Jun 28, 2026

View reviewed changes

samxu01 reviewed Jun 28, 2026

View reviewed changes

SeCuReDmE-main-dev mentioned this pull request Jun 30, 2026

RFC: Neutrosophic Consensus Engine for Multi-Agent Decision Making 2FastLabs/agent-squad#484

Closed

lilyshen0722 force-pushed the main branch from 688e208 to fcf7781 Compare July 1, 2026 23:10

Uh oh!

Conversation

SeCuReDmE-main-dev commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Linked Issue

Summary

Scope

Validation

Reviewer Notes

Uh oh!

samxu01 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

SeCuReDmE-main-dev commented Jun 24, 2026

Uh oh!

samxu01 left a comment

Choose a reason for hiding this comment

Uh oh!

samxu01 left a comment

Choose a reason for hiding this comment

Uh oh!

samxu01 left a comment

Choose a reason for hiding this comment

Uh oh!

samxu01 left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

SeCuReDmE-main-dev commented Jun 24, 2026 •

edited

Loading